This forum is closed to new posts and
responses. Individual names altered for privacy purposes. The information contained in this website is provided for informational purposes only and should not be construed as a forum for customer support requests. Any customer support requests should be directed to the official HCL customer support channels below:
Collecting data for a hang or a long delay Collecting data for a hangor long delay
If the Notes Client is unresponsive, and remains unresponsive, it may be hung.
If the Notes Client is unresponsive, and eventually becomes responsive, it is not hung, but may have had a long delay.
To determine the root cause of the hang or long delay, an NSD and Java core file need to be generated.
To do so, perform the following steps:
Open a DOS command prompt
Switch to the Notes data directory
Run ..\NSD (no args, assuming that the program dir is "above" the data directory
Run ..\NSD again for a long delay. Having 2 NSDs back to back will allow a comparison of the 2 states to ensure that it is in the same area of code at both points.
After the NSDs completes, supply these 2 sets of files, or do an ISA data collection
data\IBM_TECHNICAL_SUPPORT\nsd*.txt file
data\workspace\logs\java*.txt file "Java core"
Please supply the NSDs and JavaCores which can be used to pinpoint the hang.
Feedback response number DCOY7RC537 created by ~Michelle Brelu on 04/22/2009
For a hang situation, the diagnostic information is not triggered automatically. Please follow the following steps to collect the data
Return to top
. . For a hang situation, the diagnosti... (~Naomi Dwoachek... 22.Apr.09) 
